home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.amiga.programmer
- Path: chang.unx.sas.com!walker
- From: walker@chang.unx.sas.com (Doug Walker)
- Subject: Re: SAS/C and Memlib Problems
- Sender: news@unx.sas.com (Noter of Newsworthy Events)
- Message-ID: <DLyKHB.321@unx.sas.com>
- Date: Mon, 29 Jan 1996 19:51:11 GMT
- X-Nntp-Posting-Host: chang.unx.sas.com
- References: <4ed373$3o6@due.unit.no>
- Organization: SAS Institute Inc.
-
- In article <4ed373$3o6@due.unit.no>, Anders Granli <granli@stud.unit.no> wrote:
- >Hello!
- >
- >I have a problem with using the Memlib routines (by Doug Walker) supplied with my
- >SAS/C 6.5. I have used these routines to debug my program for a long time. Now they
- >suddenly stop working. When I compile with the memlib, my program doesn't start at
- >all. No errors are given!
- >
- >I have included the right files, in the right order, I have linked with memlib. I
- >can't understand what is wrong...
- >
- >Does anybody have a clue?
-
- Sounds like you have an old version of the compiler. We shipped one version
- (was it 6.50?) which caused memlib to break because it assumed that the
- _STI routines were going to return a value. We modified the compiler to
- return 0 for you if you declared the _STI function void, but did not
- recompile memlib, so it failed.
-
- To fix it, just make sure that you have the latest version of the compiler
- that your base release can handle (6.56 if you're at version 6.50 or above)
- and rebuild memlib from the source code. You might want to change the
- _STI routine so that it has an "int" return value and returns 0.
-
- By the way, you can debug this by using CPR with the -s (startup) option.
- CPR will stop before executing the first instruction, allowing you to
- single-step through the startup code.
-
- --
- ***** / walker@unx.sas.com
- *|_o_o|\\ Doug Walker< BIX, Portal: djwalker
- *|. o.| || \ AOL: weissblau
- | o |//
- ======
- Any opinions expressed are mine, not those of SAS Institute, Inc.
-
-